Programmable I/O interface

ABSTRACT

The invention provides an architecture and method for implementing a programmable I/O interface. The primary function provides a generic reconfigurable interface for serial communications between a laser printer controller and the print mechanism. The design also supports vertical page synchronization (top of page detection).

BACKGROUND

In the prior art, a laser printer controller is designed specifically for a dedicated print mechanism communications state machine. Thus, an application specific integrated circuit (ASIC) must be redesigned when the engine interface specification changes or when a mechanism from a different vendor is used. In addition, a laser print controller may use I/O interfaces, such as serial, parallel, control area network (CAN), and front panel with dedicated fixed function hardware. Because the functionality of the interface is fixed in a given ASIC, the flexibility is limited, and it may be unable to support changes in the protocol of a given interface. In addition, if alternate functionality is desired, the ASIC must be redesigned. For interfaces that are not well defined prior to the onset of ASIC development, the Programmable I/O can reduce implementation risk and provide time-to-market advantages.

SUMMARY

The present invention defines a programmable I/O subsystem architecture that can be used to implement a variety of I/O protocols. It is well suited for the implementation of communication interfaces between laser printer controllers and laser printer mechanism controllers. The I/O subsystem is attached to the main system processor via a traditional bus structure and may be included within a single integrated circuit or in separate integrated circuits. The I/O subsystem consists of a simple microcontroller, code store SRAM that contains the executable code, a run control register which is set by the main system CPU to enable the subsystem, and a specialized dual-port register file.

The simple microcontroller includes a simple instruction set that allows it to emulate basic state machine constructs. The architecture as described herein includes a dual-port register file that allows single-cycle read-modify-write accesses for the most efficient emulation of I/O state machines. However, a traditional microcontroller could alternatively be used with traditional registers.

The code store RAM is loaded with executable microcontroller code from the main processor prior to being enabled via the run control register. After the microcontroller is enabled, the microcontroller executes the instruction sequence stored in this memory. Although external arbitrated memory could be used for some applications, the local memory is preferable for fast and repeatable state machine sequencing of the microcontroller. Since the executable “state machine” code is downloaded by the applications processor, the I/O subsystem is configurable at run time.

The specialized dual-port register file contains a number of features that enable the I/O subsystem to efficiently implement a wide variety of protocols. The register file includes a bank of general-purpose registers, timer registers, external I/O interface registers, internal I/O registers, shared registers, an interrupt register, and an optional DMA FIFO that are used by the microprocessor for data storage. The timer registers provide real-time control and measurement of timing sequences. The external I/O interface registers with edge detection capability allows the microcontroller to sample and/or control the I/O signals that comprise the protocol.

The internal I/O interface registers can optionally be used to interface the programmable I/O system to a dedicated hardware block. The bank of shared registers, with an access protocol, which are jointly accessible by both the microcontroller and the main system CPU. An interrupt register allows interrupts to be passed from the I/O subsystem to the main CPU. The optional DMA FIFO allows efficient bulk data transfer from the I/O subsystem to/from the main system memory with minimal main system processor intervention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a system according to the present invention.

FIG. 2 illustrates an example implementation for a laser printer.

DETAILED DESCRIPTION

The invention provides an architecture and method for implementing a programmable I/O interface. The primary function provides a generic reconfigurable I/O interface. The interface can be used for communications between a laser printer controller and the print mechanism, or it can be used to implement a variety of standard or custom communications interface, e.g. serial interfaces, parallel interfaces, serial peripheral interface (SPI), Synchronous Serial Interface (SSI), MicroWire, Inter Integrated Circuit (I2C), control area network (CAN), UART, IEEE1284, LCD interface, front panel interface, and MODEM.

The invention 10, as shown in FIG. 1, is attached as a peripheral in a traditional microprocessor-based embedded system. It may be included in the same integrated circuit as the main microprocessor, or it may be in a separate integrated circuit. The invention is connected to the main microprocessors bus as a peripheral. It also attaches to the system interrupt controller and optionally to a system direct memory access (DMA) controller. As an additional option, in some cases it may also attach to a dedicated hardware feature in the integrated circuit. For example, in a video system, the invention may be used to detect synchronization pulses pertaining to a video stream.

The invention may extract the complex synchronization information and pass the simplified synchronization information to a dedicated video output controller. In a laser printer, this synchronization would include the vertical page synchronization that is passed to the laser modulation controller.

The architecture 10, shown in FIG. 1, consists of four main elements. A microcontroller 12, a code store SRAM 14, a run control register 16, and a specialized dual-port register file 18.

The microcontroller 12 includes a minimal instruction subset to emulate basic state machine constructs. To illustrate, a minimum subset can include branches, conditional branches, loops, move, increment/decrement, comparison, and simple Boolean operations. For code efficiency, a single-level stack register 24 may be included to permit single-depth subroutines. As shown on the invention diagram, an illustrative microcontroller 12 consists of a program counter (PC) 20 indicating the location in the code store 14 that is being executed, an execution unit 22 that decodes the micro-coded instruction from the code store, a stack register 24 which can store a single return address, a single-cycle arithmetic logic unit (ALU) 26 that can operate on data presented from the code store and/or current values of the register file 18, and a flag 28 which stores the result of the previous instruction for conditional branching. The executable machine code can be generated by a simple assembler. Freeware assemblers are available which can be configured to support a simple microcontroller by editing a include file that defines the opcodes and machine instruction format. A listing and symbol table is created by the assembler to help debug the code.

The code store SRAM 14 is used to contain the machine instructions that will be executed by the microcontroller 12. The code store SRAM 14 is loaded by the main system microprocessor 30 at run time. From the microcontroller 12 perspective, it is a read-only memory. After the main processor 30 has loaded the code, it signals the microcontroller 12 to begin executing instructions via the run control register 16. As an alternative implementation, an arbitrated system memory (not shown), e.g. DRAM, could be used to store the executable code. However, this is less preferable since it would reduce the state machine performance and may not yield the repeatable results that may be required to implement an I/O protocol. The I/O protocol, e.g. system programming interface (SPI), Inter Integrated Circuit (I2C), control area network (CAN), RS232, IEEE1284, front panel, and MODEM, is defined by the executable “state machine” code.

The heart of the invention is the specialized register file 18. The register file 18 is what allows the invention to operate efficiently as an I/O subsystem with minimal overhead on the main system processor. In effect, these features allow the programmable I/O to appear very much like a dedicated hardware peripheral. The invention provides capabilities that are normally found in a dedicated hardware peripheral, including peripheral status/configuration/control registers, interrupt capability, and DMA capability for bulk data transfer.

Ideally, the specialized register file 18 is dual-ported to allow the simple microcontroller 12 to perform read-modify-write operations for code-size efficiency and performance. The register file 18 may include a bank of general-purpose microcontroller registers 18A, timer registers 18B, external I/O interface registers 18D, internal I/O registers 18E, shared registers 18C, an interrupt register 18F, and an optional DMA FIFO 18G that are used by the microprocessor 30 for data storage.

The general-purpose microcontroller registers 18A are used for local variables and storage.

The Timer Registers 18B are similar to the General Purpose Registers 18A. They may be configured to increment independently based on a selected system timebase (e.g. 1 us, 10 us, 100 us, 1 ms, 10 ms, and 100 ms). They are used to generate timing for the protocol to be implemented and for detecting protocol timeout errors. The registers may be configured to stop at a predetermined terminal count or can be free running.

The shared registers 18C may be accessed by both the main system processor 30 as well as the I/O microcontroller 12. They are used to emulate the peripheral status/configuration/control registers that appear in a traditional hardware peripheral. For efficiency, the registers 18C may be accessed differently by the main processor 30 and the microcontroller 12. For example, the main processor 30 may read four byte-wide registers at once as a single 32-bit word, whereas, the microcontroller 12 may access them as 4 separate 8-bit entities. In order to efficiently and safely implement a status/protocol in these registers 18C, an access priority is specified which grants write access for a particular register to either the main processor 30 or the microcontroller 12. The method for access priority control is specified in a separate patent application disclosed by Richard Taylor, “Register Access Protocol for Multi-Processor Systems”, assigned to Agilent Technologies, filed 11 Mar. 2004 with the United States Patent and Trademark Office.

The external I/O interface registers 18D allow the microcontroller 12 to observe and control the actual external electrical signals that comprise the protocol of the communications that is to be implemented. These registers 18D include additional functionality to permit efficient implementation of the control state machine in the microcontroller 12. Registers 18D are provided so that each signal can be defined as an input, output, or bidirectional signal. If input, the state of the signal can be read. Synchronizers are provided on each input to prevent asynchronous issues. In addition, optional edge detect logic is provided to indicate if a rising or falling edge has occurred on the input signal. The transition detection is particularly valuable if the I/O protocol consists of pulses that could otherwise have been missed. When a signal is used as on output, the output level and output enable is directly controlled by the registers 18D.

The internal I/O interface registers 18E. This provides a similar function to the external I/O interface registers 18E, except that it allows the I/O subsystem to communicate with internal dedicated function blocks. This is useful when the purpose of the programmable I/O subsystem is to serve as a flexible intermediary between an external protocol and an internal fixed-function peripheral. As an example, for a laser printer controller, there is a dedicated laser printer modulation output controller that creates a serial video bitstream that fires the laser. The bitstream must be synchronized to the actual position of the photosensitive drum and the paper. The method of horizontal and vertical synchronization varies among the available print mechanisms. Some mechanisms may provide a single vertical synchronization signal, others may require the vertical synchronization to be inferred by the presence of a horizontal synchronization signal, or others may provide numerous vertical synchronization signals for multiple drums. The I/O subsystem may be used to decode the synchronization implemented in a particular mechanism and translate it to a consistent synchronization interface to the dedicated modulation controller. The programmable nature of the invention allows the design to support a variety of mechanisms, as well as mechanisms that have not yet been defined.

The interrupt register 18F would allow the I/O subsystem to provide interrupt-driven status to the main processor 30, as would a traditional peripheral. In actual implementation, the interrupt register 18F may be included in the shared registers 18C, with additional dedicated interrupt signals to the main system processor 30.

The FIFO 18G allows bulk data transfer to be completed between the I/O subsystem and system memory with minimal support required by the main system processor 30. Data written to the FIFO 18G by the microcontroller 12 is transferred via DMA 34 to the main system memory (not shown). Likewise, incoming DMA data may be read by the microcontroller 12. The run control register 16 may include a feature to clear the contents of the FIFO 18G.

Given the programmable nature of the invention, different communication protocols can be supported with a single design. ASIC designs can be completed before the communications protocol is fully defined. The controller, interface timing, and protocol may be modified late in the design cycle or in the field. Higher degrees of hardware assist may be implemented. The design can be used to implement new interfaces that were not yet conceived at the time the ASIC design was released.

The invention is particularly suited for laser printers. In an example implementation, shown in FIG. 2, a single controller 12 is used to provide both the serial command/status channel between the laser modulation controller 36 and the mechanism controller (separate integrated circuit) 38, as well as the vertical page synchronization. The design supports a variety of color and monochrome print mechanisms with varying numbers laser beams, due to the ability to download different synchronization protocols. 

1. A programmable interface comprising: a register file having a plurality of registers, each register having a type; a run control register; a microcontroller configured to bidirectionally communicate with the register file and the run control register; a Code Store SRAM configured to bidirectionally communicate with the microcontroller; and executable code including one or more instructions; wherein the Code Store SRAM and the run control register are configured to bidirectionally communicate with a system processor that is external to the programmable interface; and wherein the system processor is configured to load the executable code onto the Code Store SRAM and is further configured to signal the microcontroller, via the run control register, to begin execution of the one or more instructions included in the executable code; and wherein the plurality of registers includes (i) a general-purpose microcontroller register, (ii) a timer register, (iii) an external input/output (I/O) interface register, (iv) an internal I/O register, (v) a shared register, (vi) an interrupt register, and (vii) a first-in, first-out (FIFO) register configured to communicate with a direct memory access (DMA) controller.
 2. A programmable interface, as defined in claim 1, wherein the external I/O interface register includes an edge detect logic.
 3. A programmable interface, as defined in claim 1, wherein the executable code implements a laser printer mechanism communications interface and a vertical top-of-page synchronization interface.
 4. A programmable interface, as defined in claim 1, wherein the executable code is selected from a group that includes serial interfaces, parallel interfaces, serial peripheral interface (SPI), Synchronous Serial Interface (SSI), MicroWire, Inter Integrated Circuit (I2C), control area network (CAN), UART, IEEE1284, LCD interface, front panel interface, and MODEM.
 5. A programmable interface, as defined in claim 1, wherein the system processor is configured to bidirectionally communicate with the register file.
 6. A programmable interface, as defined in claim 1, wherein the timer register is configured to (i) increment independently based on a selected system timebase, (ii) generate timing for protocols to be implemented, and (iii) detect protocol timeout errors.
 7. A programmable interface, as defined in claim 1, wherein the shared register is accessed by both the system processor and the microcontroller, and wherein the shared register is configured to emulate a peripheral status, wherein an access priority grants write access to either the system processor or the microcontroller for accessing the to the shared register.
 8. A programmable interface, as defined in claim 1, wherein the external I/O interface register is configured to (i) facilitate the microcontroller to observe and control actual external electrical signals associated with a protocol of communications of the programmable interface, and (ii) facilitate implementation of a control state machine in the microcontroller.
 9. A programmable interface, as defined in claim 1, wherein the internal I/O register is configured to (i) facilitate an I/O subsystem to communicate with internal dedicated function blocks of the programmable interface.
 10. A programmable interface, as defined in claim 1, wherein the interrupt register is configured to (i) facilitate an I/O subsystem to provide interrupt-driven status to the system processor. 